-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Add FIRAppCheckProtocol to FirebaseAppCheckInterop SDK
#11660
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Coverage Report 1Affected Products
Test Logs |
Apple API Diff ReportCommit: 2c1f46c FirebaseAppCheckClassesFIRAppCheck[REMOVED] -tokenForcingRefresh:completion:Swift:
- func token ( forcingRefresh : Bool ) async throws -> FIRAppCheckToken
Objective-C:
- - ( void ) tokenForcingRefresh :( BOOL ) forcingRefresh completion :( nonnull void ( ^ )( FIRAppCheckToken * _Nullable , NSError * _Nullable )) handler ;[REMOVED] -limitedUseTokenWithCompletion:Swift:
- func limitedUseToken () async throws -> FIRAppCheckToken
Objective-C:
- - ( void ) limitedUseTokenWithCompletion : ( nonnull void ( ^ )( FIRAppCheckToken * _Nullable , NSError * _Nullable )) handler ; |
These signatures are now in FIRAppCheckProtocol.
821c936 to
a6029d1
Compare
|
When I attempt to update react-native-firebase to firebase-ios-sdk 10.16.0, including this PR, I receive this:
I traced it to this PR when I noticed that header file changed in my pod cache between 10.15.0 and 10.16.0. Is this an expected outcome? (stated differently, is there something I need to change so this works, ideally that wouldn't be a breaking change for us since we're adopting a feature release here...) It's coming from here: ...and that file doesn't go through with our compiler settings 🤔 Is there anything that can be done here? In issues past, I have attempted to provide build instructions for our test app over in react-native-firebase so reproductions are easy but I/we have observed you all may have difficulty since it requires a relatively up to date javascript / node environment etc etc and that's a time suck if you don't already have it running. Let me know if you want repro instructions or any other information though, happy to collaborate of course |
|
@mikehardy Thanks for the report. We had an internal report of the same Objective C++ breakage earlier today so we shouldn't need a repro. We plan to fix for the next release and expect to have the details sorted out in the next few days. Feel free to open an issue for tracking. Roughly, a workaround is something like replacing the |
|
Okay, I opened #11916 but noted right at the top that this was known and in progress, just for tracking I don't think as a cocoapods consumer there is a clean way for us to work around it. Just as an exercise, I tried hacking with the cocoapods cache versions of the App Chck podspec to include the interop headers in source files, and then adjust the Thanks! |
Added a protocol named
FIRAppCheckProtocolto theFirebaseAppCheckInteropSDK that duplicates the token fetching public APIs ofFIRAppCheck. UpdatedFIRAppCheckto publicly conform toFIRAppCheckProtocol.This will allow other SDKs to accept an instance of App Check through a parameter of type
id<FIRAppCheckProtocol>, while not requiring a hard dependency onFirebaseAppCheck.#no-changelog